Devices and methods for selective contactless communication

ABSTRACT

A card having an antenna, one or processors, and memory having stored thereon a first application and a second application configured to receive an input of the card and determine a request associated with the input. The card is further configured to activate, responsive to determining that the request is consistent with a contactless EuroPay-MasterCard-Visa (EMV) data standard, the first application. The first application is configured to communicate, via near field communication (NFC), data to the communicating device via the antenna based on the EMV data standard for payment purposes. The card is further configured to activate, responsive to determining that the request is consistent with a near field communication data exchange format (NDEF) standard, the second application. The second application is configured to communicate, via NFC, data to the communicating device via the antenna based on the NDEF standard for verification/identification purposes.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY CLAIM

This application is a continuation of, and claims priority under 35U.S.C. § 120 to, U.S. patent application Ser. No. 16/223,403, of thesame title, filed on Dec. 18, 2018, the entire contents of which arehereby incorporated by reference.

FIELD

The presently disclosed subject matter relates generally to contactlesscommunication devices configured to communicate with other devices and,more particularly, to contactless cards configured to selectivelycommunicate different types of data and/or using different protocols todifferent types of other devices.

BACKGROUND

Contactless cards may be used for many purposes including for payment,access, or identification. For example, some types of contactless cards,including contactless credit cards, are configured to communicate with apayment terminal to transmit payment data when purchasing an item ormaking a payment. It may be advantageous to configure such paymentcontactless cards, including contactless credit cards, to also enablecommunication of identification data (or perform other authenticationfunctions) with a mobile device or another computing device distinctfrom a payment transaction with a payment terminal, such as when a useris logging into an application on the mobile device to access a securedfeature or payment function. Care should be taken, however, todistinguish between the different uses or functions of the contactlesscard and to limit the communications to only the data required for eachuse or function between the contactless card and the device.

Accordingly, the present disclosure is directed to embodiments ofcontactless cards, devices, and related methods configured to provideselective communications for improving data security of thecommunications when capable of communicating with different devicesand/or for different functions.

SUMMARY

Aspects of the disclosed technology include devices and methods for acard capable of selective communications with a plurality of devicetypes. Consistent with the disclosed embodiments, certain methods mayutilize one or more communicating devices (e.g., mobile device,point-of-sale terminal device) and one or more contactless devices(e.g., radio frequency identification (RFID) cards). A method mayinclude a first connection established between a card and a firstdevice. After a data format of the first connection is determined to bea first data format, a first application of the card transmits paymentdata. The method may further include a second connection establishedbetween the card and a second device. After a data format of the secondconnection is determined to be a second data format, a secondapplication of the card transmits identification data.

In some embodiments, the first device is a point-of-sale device and thefirst data format corresponds to a EuroPay-MasterCard-Visa (EMV) datastandard. According to some embodiments, the second device is a mobiledevice, and the second data format corresponds to a near fieldcommunication data exchange format (NDEF) data standard. In thedisclosed embodiments, the method may further include the cardcommunicating with the mobile device and/or the point-of-sale device byusing near field communication (NFC). The card may have a radiofrequency identification (RFID) chip. Communication between the card andthe device may occur when the RFID chip of the card is within an NFCrange of a digital reader. The card may receive, from the mobile device,one or more instructions to generate a digital signature. In response,the card may generate the digital signature. The digital signature maybe generated using a private key of a key pair or other secret. The cardmay transmit the digital signature to the mobile device.

In some embodiments, a card may have an antenna, one or more processors,and a memory storing instructions along with a first application and asecond application. The card may receive and/or transfer data to acommunicating device. Optionally, the card may include a sensorconfigured to detect, in cooperation with the antenna, an input of thecard from a communicating device. Regardless of how the card input ofthe card is received, the card may be configured to determine a format(e.g., a data format) of the input in response to detecting the input ofthe card. In some embodiments, a data format may be determined from theinput itself, in other embodiments, a data format may be determinedbased on an identifier associated with the first or second application,or any other indicia from which the data format may be determined. Inresponse to determining the data format is a EuroPay-MasterCard-Visa(EMV) data standard, the card may be configured to activate the firstapplication. The first application may be configured to communicate, viaNFC, payment data to the communicating device via the antenna based onthe EMV data standard. In response to determining the data format is aNDEF data standard, the processor may activate the second application.The second application may be configured to communicate, via NFC,identification data to the communicating device via the antenna based onthe NDEF standard. The card may be a contactless payment card,contactless identification card, or any device capable of transmittingdata through an NFC standard and/or an EMV standard. The card may beconfigured to send only one of the payment data and the identificationdata to a single communicating device. The first application may beunable to access the identification data and the second application maybe unable to access the payment data.

In some embodiments, the card may further include a radio frequencyidentification (RFID) chip. In those embodiments, the communicatingdevice may be a mobile device. The second application may be configuredto communicate with the mobile device using the NFC standard when theRFID chip is within an NFC range of a digital reader associated with themobile device. The second application may also transmit a public key ofa key pair of the card to the mobile device and receive, from the mobiledevice, one or more instructions to generate a digital signature. Thesecond application may further generate the digital signature using aprivate key of the key pair of the card and transmit the digitalsignature to the mobile device.

In further embodiments, a card may have an antenna, a radio frequencyidentification (RFID) chip, one or more processors, and a memory havinga first application and a second application. The sensor may beconfigured to detect an input of the card via the antenna. The firstapplication may be configured to communicate with a first device basedon a first format of the input. The second application may be configuredto communicate with a second device based on a second format of theinput. The card may be configured to prevent communication between thefirst application and the second application. The card may be acontactless payment, contactless identification card, or any devicecapable of transmitting data through an NDEF data standard and/or an EMVdata standard. The first format may be a EuroPay-MasterCard-Visa (EMV)data standard. The card may be configured to communicate, by the firstapplication and through the EMV data standard, with the first device,which may be a point-of-sale device. The card may be further configuredto transmit payment data, by the first application, and to thepoint-of-sale device. The second format may be a NDEF data standard. Thecard may be configured to communicate, by the second application andthrough the NDEF data standard, with the second device, which may be amobile device. The card may be further configured to transmitidentification data, by the second application, and to the mobiledevice.

In some embodiments, the second application may be further configured tocommunicate with the mobile device using the NDEF data standard when theRFID chip is within an NFC range of a digital reader associated with themobile device. The second application may also transmit a public key ofa key pair of the card to the mobile device and receive, from the mobiledevice, one or more instructions to generate a digital signature. Thesecond application may generate the digital signature using a privatekey of the key pair of the card and transmit the digital signature tothe mobile device.

In an exemplary use case, a cardholder may seek to make a payment withhis credit card (e.g., contactless payment card). The cardholder maypresent the card at a merchant where the card is tapped against apoint-of-sale device. The card may determine the device type as being apoint-of-sale device. Accordingly, the card may transmit, from anapplication according to a communication protocol associated with thepoint-of-sale device, only the payment data to the point-of-sale device.When the payment data is received by the point-of-sale device, the datais used to make a transaction authorization decision. In this instance,the payment is approved, and the cardholder is able to complete hispurchase.

Further features of the disclosed design, and the advantages offeredthereby, are explained in greater detail hereinafter with reference tospecific example embodiments illustrated in the accompanying drawings,wherein like elements are indicated be like reference designators.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and which are incorporated into andconstitute a portion of this disclosure, illustrate variousimplementations and aspects of the disclosed technology and, togetherwith the description, serve to explain the principles of the disclosedtechnology. In the drawings:

FIGS. 1A-B are diagrams of an example environment that may be used toimplement one or more embodiments of the present disclosure.

FIG. 2 is a timing diagram providing selective communications with aplurality of device types according to an example embodiment.

FIG. 3 is a flow chart of a method providing selective communicationswith a plurality of device types according to an example embodiment.

FIG. 4 is a flow chart of a method providing selective communicationswith a certain device type according to an example embodiment.

FIG. 5 is a block diagram of an example computer system that mayimplement certain aspects of the present disclosure.

DETAILED DESCRIPTION

Some implementations of the disclosed technology will be described morefully with reference to the accompanying drawings. The disclosedtechnology may, however, be embodied in many different forms and shouldnot be construed as limited to the implementations set forth herein. Thecomponents described hereinafter as making up various elements of thedisclosed technology are intended to be illustrative and notrestrictive. Many suitable components that would perform the same orsimilar functions as components described herein are intended to beembraced within the scope of the disclosed electronic devices andmethods. Such other components not described herein may include, but arenot limited to, for example, components developed after development ofthe disclosed technology.

It is also to be understood that the mention of one or more method stepsdoes not preclude the presence of additional method steps or interveningmethod steps between those steps expressly identified.

Reference will now be made in detail to exemplary embodiments of thedisclosed technology, examples of which are illustrated in theaccompanying drawings and disclosed herein. Wherever convenient, thesame reference numbers will be used throughout the drawings to refer tothe same or like parts.

FIGS. 1A-B show an example environment 100 a and 100 b, respectively,that may implement certain aspects of the present disclosure. Thecomponents and arrangements shown in FIGS. 1A-B are not intended tolimit the disclosed embodiments as the components used to implement thedisclosed processes and features may vary. As shown in FIGS. 1A-B, insome embodiments, the environment 100 a-b includes a mobile device 140,a point-of-sale device 150, and a card 120 which includes an antenna122, a sensor 124, one or more processors 126 and a memory 130 havingthereon a first application 132 and a second application 134. In someembodiments, card 120 b may include a radio frequency identification(RFID) chip 136. As non-limiting examples, the mobile device 140 may bea smartphone, a laptop computer, a tablet, or other personal computingdevice. The mobile device 140 may run and display one or moreapplications and the related output(s) of the one or more applications(e.g., through APIs). The mobile device 140 may include a card reader orone or more components that may function to read from and/or communicatewith a card (e.g., a digital card reader). In conjunction with the oneor more applications, the card reader communicates with the one or morecards 120 b (e.g., RFID cards). An example computer architecture thatmay be used to implement one or more of the mobile device 140 and thepoint-of-sale device 150 is described below with reference to FIG. 5.

In certain embodiments, the cards 120 a and 120 b may be configured toreceive an input from a communicating device (e.g., mobile device 140,point-of-sale device 150). The input may include a request for data fromthe card 120 a-b. The input may include a request to establishcommunication with the card 120 a-b. The sensor 124 may detect theinput, e.g., by detecting specific input sequences. In detecting theinput, the sensor 124 may receive the input via the antenna 122. Forexample, in some embodiments, an application executing on mobile device140 may communicate with a card 120 after a card reader of the mobiledevice is brought sufficiently near the card 120 so that NFC datatransfer is enabled between the mobile device 140 and the card 120. Forcommunications involving card contact, the contact plates of the EMVchip may be involved in detecting the input. Detecting the input incontactless card communications may involve the communications methoddefined in ISO 14443. The one or more processors 126 may determine aformat (e.g., data format) of the input. For example, the format may bean NDEF data standard, a EuroPay-MasterCard-Visa (EMV) data standard,and/or the like. In some cases, the communication between the card 120a-b and the communicating device may be through application protocoldata units (APDUs).

According to some example embodiments consistent with the presentdisclosure, communication with cards 120 a and 120 b may involveApplication Protocol Data Units (APDUs). When an application isselected, specific APDU messages are exchanged. For example, in EMV,there are various certificate exchanges, and requests for signingtransaction data. For RFID type applications, the application isselected, and then File select and then File read commands are sent.

In response to receiving data consistent with an EMV data standard, theone or more processors 126 may activate the first application 132. As anon-limiting example, the one or more processors 126 may include a statemachine with various transitions governed by the outcome of authenticitytests at various states. If the received data is consistent with the EMVstandard, the data will pass an authentication check for the EMVstandard, and the state machine may move to a state where the firstapplication 132 is activated. Activating the first application 132 mayinclude initiating communication directly and/or indirectly between thefirst application 132 and the point-of-sale device 150. Once activated,the first application 132 may communicate, via NFC, payment data to thepoint-of-sale device 150. Payment data may include a cardholder'sinformation (e.g., first name, last name, address), card information(e.g., card number, expiration date, security code), and/or details ofthe transaction (e.g., transaction amount, merchant name). In someembodiments, the first application 132 is configured for communicatingpayment data specifically to payment terminals or other point-of-saledevices based on the EMV standard. In some embodiments, the firstapplication 132 (or an additional application) may communicateidentification data using similar EMV based techniques tonon-point-of-sale devices for identification or authentication purposeswithout initiating a payment transaction, as described for example, inU.S. patent application Ser. No. 16/135,954, filed Sep. 19, 2018 titled“System and Methods for Providing Card Interactions,” the contents ofwhich are expressly incorporated by reference herein in its entirety.

In response to receiving data consistent with an NDEF data standard, theone or more processors 126 may activate the second application 134. As anon-limiting example, the one or more processors 126 may include a statemachine with various transitions governed by the outcome of authenticitytests at various states. If the received data is consistent with theNDEF standard, the data will pass an authentication check for the NDEFstandard, and the state machine may move to a state where the secondapplication 134 is activated. In some embodiments, the received data mayinclude a read request, such as an NFC read, of an NDEF tag, which maybe created in accordance with the NDEF data standard. For example, areader of the mobile device 140 may transmit a message, such as anapplet select message, with an applet ID of an NDEF producing appletstored on the card 120. Processors 126 may thus determine that the formof the input is consistent with an NDEF request based on the applet IDor other indicia for example. Data consistent with an NDEF standard maybe formatted in a modified form of Type Length Value (TLV) encoding withspecific Type bytes encoding various parts of the NDEF message. NFC NDEFinformation is conveyed in a single NDEF message which can be brokeninto records. In some embodiments, each record may be further brokeninto multiple parts. Activating the second application 134 may includeinitiating communication directly and/or indirectly between the secondapplication 134 and the mobile device 140. Once activated, the secondapplication 134 may communicate, via NFC, identification data to themobile device 140. Identification data may include any data used toverify or authenticate identity. For example, identification data mayinclude a cryptogram or signature associated with the card 120. Further,identification data may, but need not include any actual identificationinformation of the user. In some embodiments, identification datatransmitted via NFC Data Exchange Format One True Pairing (NDEF OTP) maybe used to validate an online transaction with an entered card numberwithout requiring a merchant payment system for EMV.

In some embodiments, the card 120 b may include a radio frequencyidentification (RFID) chip 136. The card 120 a-b may communicate withthe mobile device 140 when the card 120 a-b is within an NFC range of adigital reader of the mobile device 140. More specifically, the secondapplication 134 may communicate directly and/or indirectly with themobile device 140. In some embodiments, communication may involvetransmitting a public key of a key pair of the card 120 b to the mobiledevice 140. The card 120 b may receive from the mobile device 140 one ormore instructions to generate a digital signature. Using a private keyof the key pair of the card 120 b, the second application 134 maygenerate the digital signature. The card 120 b may transmit the digitalsignature to the mobile device 140, based on which card 120 b (and/orits user) may be authenticated. In some embodiments, the card 120 b mayreceive a request from the mobile device 140 (e.g. from an applicationon the mobile device configured to transmit the request) comprising aninstruction to generate a cryptogram, from which the card 120 b may beauthenticated. For example, the cryptogram may be a messageauthentication code (MAC) cryptogram as described in U.S. patentapplication Ser. No. 16/205,119, filed on Nov. 29, 2018, titled “Systemsand Methods for Cryptographic Authentication of Contactless Cards,” thecontents of which are expressly incorporated herein in its entirety.

The cards 120 a-b may be configured to send only one of the payment dataand the identification data to a single communicating device (e.g.,mobile device 140, point-of-sale device 150). For example, cards 120 a-bmay isolate the payment data and the identification data from differentapplications (e.g., first and second applications 132 and 134).Accordingly, when the first application 132 is activated, a first set ofdata is available for transmission and when the second application 134is activated, a second set of data is available for transmission.Further, the first application 132 may be unable to access theidentification data and the second application may be unable to accessthe payment data. According to some embodiments, the cards 120 a-b maytransmit only payment data or only identification data based on arequest from point-of-sale device 150 or mobile device 140,respectively.

Turning to the mobile device 140, in some embodiments, the mobile device140 may include a digital card reader and/or one or more applications.The mobile device 140 may be configured to transmit an input to the card120 a-b. The input may provide data indicative of a particular dataexchange format. For example, the data may be consistent with datatransmitted in an EMV data standard, an NDEF data standard, and/or othercomparable data exchange standards. For example, the mobile device 140may communicate, via NFC, and based on the NDEF data standard with thesecond application 134. The mobile device 140 may receive identificationdata from the card 120 a-b. The mobile device 140 may receive a publickey of a key pair of the card 120 b. In response, the mobile device 140may transmit one or more instructions to generate a digital signature tothe card 120 b. The mobile device 140 may receive the generated digitalsignature from the card 120 b.

The point-of-sale device 150 may include one or more of a monitor, oneor more processors, and a digital reader capable of performing NFC. Thepoint-of-sale device 150 may communicate, via NFC and based on the EMVdata standard, with the first application 132. The point-of-sale device150 may receive payment data from the card 120 a-b.

FIG. 2 is a timing diagram of providing selective communications with aplurality of device types. According to some embodiments, at 202, thepoint-of-sale device 150 may send a first input (e.g. communication,request, etc.) to the card 120 a. The antenna 122 may receive the firstinput. The input may be indicative of a data format (e.g., EMV datastandard). At 204, the antenna 122 may communicate the first input tothe sensor 124. The sensor 124 may detect the first input at 206 (e.g.,by differentiating the input from noise), and communicate the existenceof the first input with the processor 126 at 207. At 208, theprocessor(s) 126 may determine the format of the input. In someembodiments, a program (e.g., an applet) associated with theprocessor(s) 126 can determine the format of the input based on anidentification activation sequence. Such the identification activationsequence may be used to select a specific application for activation. Inresponse to determining that the format of the received data isconsistent with an EMV data standard, at 210, the processor 126activates the first application 132. Activating the first application132 may involve establishing communication between the processor 126 andthe first application 132. Further, the processor(s) 126 may communicatethe input and/or the data format to the first application 132. At 212,the first application 132 may communicate the payment data, for output,to the antenna 122. In some embodiments, prior to transmitting paymentdata to the point-of-sale device 150, the card 120 verifies thepoint-of-sale device 150 by exchanging digital signatures andestablishing trust with the point-of-sale device 150 via CertificateAuthority (CA) chains. At 214, the antenna 122 transmits the paymentdata the point-of-sale device 150. In some embodiments, as discussedabove, a first application 132 may also be configured to communicate fornon-payment purposes, such as for authentication or identification, to anon-point-of-sale device, such as mobile device 140, using the EMV datastandard.

At 216, the mobile device 140 may send a second input to the card 120 a.The antenna 122 receives the second input. The input may be indicativeof a data format (e.g., an NDEF data standard). At 218, the antenna 122may communicate the second input to the sensor 124. The sensor 124detects the second input at 220 (e.g., by differentiating the input fromnoise), and communicates the existence of the second input with theprocessor 126 at 221. Detecting the input may involve deciphering theinput from the mobile device 140 such that the data format is at leastrecognized by the card 120 a. At 222, the processor(s) 126 may determinethe format of the input. At 224, in response to determining that theformat is consistent with a contactless NDEF data standard, theprocessor 126 activates the second application 134. Activating thesecond application 134 may involve establishing communication betweenthe processor(s) 126 and the second application 134. Further, theprocessor(s) 126 may communicate the input and/or the data format to thesecond application 134. At 226, the second application 134 maycommunicate the identification data, for output, to the antenna 122. At228, the antenna 122 transmits the identification data the mobile device140.

In an example scenario, a customer or user is seeking to pay a merchantwho is using a smartphone (e.g., mobile device 140) equipped with adigital reader. The customer taps his credit card (e.g., 120 a-b)against the merchant's smartphone such that NFC communication isestablished. The smartphone may be equipped with a payment applicationrequiring both identification data and payment data in order to processa transaction. The credit card receives an input from the smartphone.The input includes data consistent with an NDEF data standard.Responsive to determining data consistent with the NDEF data standard,the credit card transmits identification data to the smartphone. Thesmartphone verifies the cardholder's identity and then sends a secondinput consistent with an EMV data standard. After determining the EMVdata standard, the credit card transmits payment data to the smartphone.The smartphone verifies the payment information and completes thetransaction.

FIG. 3 is a flow chart of a method providing selective communicationswith a plurality of device types. At 302, a first connection between thecard 120 a-b and the first device (e.g., point-of-sale device 150) isestablished. Establishing a first connection between the card 120 a-band the point-of-sale device 150 may involve bringing the card 120 a-bwithin an NFC range of a digital reader of the point-of-sale device 150.Establishing a first connection may further involve receipt of an inputby the card 120 a-b from the point-of-sale device 150. At 304, the dataformat of the first connection may be determined by the processor 126.The data format of the first connection may be consistent with an EMVdata standard, an NDEF data standard, or another data standard capableof transmitting data via an NFC. For example, the processor 126determines the data format of the first connection is consistent with anEMV data standard. At 306, in response to determining the data format isconsistent with an EMV data standard, the card 120 a-b transmits thepayment data to the point-of-sale device 150. In some embodiments, thefirst application 132 may output, for transmission, the payment data tothe point-of-sale device 150.

At 308, a second connection between the card 120 a-b and the seconddevice (e.g., mobile device 140) is established. Establishing a secondconnection between the card 120 a-b and the mobile device 140 mayinvolve bringing the card 120 a-b within an NFC range of a digitalreader of the mobile device 140. Establishing a second connection mayfurther involve receipt of an input by the card 120 a-b from the mobiledevice 140. At 310, the data format of the second connection may bedetermined by the processor 126. The data format of the secondconnection may be consistent with an EMV data standard, an NDEF datastandard, or another data standard capable of transmitting data via anNFC. Here, the processor 126 determines the data format of the secondconnection is consistent with an NDEF data standard. At 312, in responseto determining the data format is consistent with an NDEF data standard,the card 120 a-b transmits the identification data to the mobile device140. In some embodiments, the second application 134 may output, fortransmission, the identification data to the mobile device 140.

FIG. 4 is a flow chart of a method providing selective communicationswith a certain device type. The method described herein involves a card120 a-b and a mobile device 140 and further details certain steps inauthenticating identification information. At 402, a connection betweenthe card 120 a-b and the mobile device 140 is established. Theconnection may be established when the card 120 a-b is placed within anNFC range of a digital reader associated with the mobile device 140. At404, the processor 126 may determine the data format of the connectionis consistent with an NDEF data standard. At 406, the card 120 a-b mayfurther communicate with the mobile device 140 via NFC. Thecommunication may be used to authenticate the identification data of thecard 120 a-b. At 408, the card 120 a-b transmits a public key of a keypair of the card 120 a-b to the mobile device 140. At 410, the card 120a-b receives instructions to generate a digital signature from themobile device 140. Based on the received instructions from the mobiledevice 140, the card 120 a-b generates a digital signature using aprivate key of the key pair of the card 120 a-b, at 412. In some cases,the identification information may be incorporated within the digitalsignature or otherwise conveyed with the digital signature. At 414, thecard 120 a-b transmits the digital signature to the mobile device 140.In some embodiments, the digital signature may be any form of cryptogrambased on a secret known by the card 120 a-b and/or generated by the card120 a-b, not necessarily a private key of a key pair. For example, anycryptographic technique for reliably verifying the authenticity of card120 a-b may be used.

FIG. 5 is a block diagram of an example computer system 500 that mayimplement certain aspects of the present disclosure. The computer system500 may include a set of instructions 526 for controlling operation ofthe computer system 500. In some implementations, the computer system500 may be connected (e.g., networked) to other machines in a Local AreaNetwork (LAN), an intranet, an extranet, a satellite communicationssystem, or the Internet. The computer system 500 may operate in thecapacity of a server or a client machine in a client-server networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The computer system 500 may be a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a server, a networkrouter, switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while a single computer system 500 isillustrated, the term “machine” shall also be taken to include anycollection of machines (e.g., computers) that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methodologies discussed herein.

The computer system 500 includes a processing device 502, a main memory504 (e.g., read-only memory (ROM), flash /.memory, dynamic random-accessmemory (DRAM) such as synchronous DRAM (SDRAM), etc.), a static memory506 (e.g., flash memory, static random-access memory (SRAM), etc.), anda secondary memory 516 (e.g., a data storage device), which communicatewith each other via a bus 508.

The processing device 502 represents one or more general-purposeprocessing devices such as a microprocessor, a microcontroller, acentral processing unit, or the like. As non-limiting examples, theprocessing device 502 may be a reduced instruction set computing (RISC)microcontroller, a complex instruction set computing (CISC)microprocessor, a RISC microprocessor, very long instruction word (VLIW)microprocessor, a processor implementing other instruction sets, or oneor more processors implementing a combination of instruction sets. Theprocessing device 502 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 502 is configuredto execute the operations for electronically creating and tradingderivative products based on one or more indices relating to volatility.

The computer system 500 may further include a network interface device522, which is connectable to a network 530. The computer system 500 alsomay include a video display unit 510, i.e., a display (e.g., a liquidcrystal display (LCD), a touch screen, or a cathode ray tube (CRT)), analphanumeric input device 512 (e.g., a keyboard), a cursor controldevice 514 (e.g., a mouse), and a signal generation device 520 (e.g., aspeaker).

The secondary memory 516 may include a non-transitory storage medium 524on which is stored one or more sets of instructions 526 for the computersystem 500 representing any one or more of the methodologies orfunctions described herein. For example, the instructions 526 mayinclude instructions for implementing an asset tracking device includinga power source and power management system or subsystem for a containeror a trailer. The instructions 526 for the computer system 500 may alsoreside, completely or at least partially, within the main memory 504and/or within the processing device 502 during execution thereof by thecomputer system 500, the main memory 504 and the processing device 502also constituting computer-readable storage media.

While the storage medium 524 is shown in an example to be a singlemedium, the term “storage medium” should be taken to include a singlemedium or multiple media that store the one or more sets of instructionsfor a processing device. The term “storage medium” shall also be takento include any medium that is capable of storing or encoding a set ofinstructions for execution by the machine that cause the machine toperform any one or more of the methodologies of the disclosure. The term“storage medium” shall accordingly be taken to include, but not belimited to, solid-state memories, and optical and magnetic media.

Throughout the specification and the claims, the following terms take atleast the meanings explicitly associated herein, unless the contextclearly dictates otherwise. The term “or” is intended to mean aninclusive “or.” Further, the terms “a,” “an,” and “the” are intended tomean one or more unless specified otherwise or clear from the context tobe directed to a singular form.

In this description, numerous specific details have been set forth. Itis to be understood, however, that implementations of the disclosedtechnology may be practiced without these specific details. In otherinstances, well-known methods, structures and techniques have not beenshown in detail in order not to obscure an understanding of thisdescription. References to “one embodiment,” “an embodiment,” “someembodiments,” “example embodiment,” “various embodiments,” “oneimplementation,” “an implementation,” “example implementation,” “variousimplementations,” “some implementations,” etc., indicate that theimplementation(s) of the disclosed technology so described may include aparticular feature, structure, or characteristic, but not everyimplementation necessarily includes the particular feature, structure,or characteristic. Further, repeated use of the phrase “in oneimplementation” does not necessarily refer to the same implementation,although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

While certain implementations of the disclosed technology have beendescribed in connection with what is presently considered to be the mostpractical and various implementations, it is to be understood that thedisclosed technology is not to be limited to the disclosedimplementations, but on the contrary, is intended to cover variousmodifications and equivalent arrangements included within the scope ofthe appended claims. Although specific terms are employed herein, theyare used in a generic and descriptive sense only and not for purposes oflimitation.

This written description uses examples to disclose certainimplementations of the disclosed technology, including the best mode,and also to enable any person skilled in the art to practice certainimplementations of the disclosed technology, including making and usingany devices or systems and performing any incorporated methods. Thepatentable scope of certain implementations of the disclosed technologyis defined in the claims, and may include other examples that occur tothose skilled in the art. Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral language of the claims.

Exemplary Use Cases

The following example use cases describe examples of particularimplementations of a cardholder using a contactless card for selectivecommunication. These examples are intended solely for explanatorypurposes and not limitation. In one case, a cardholder seeks to pay amerchant for items purchased at the merchant's store. When the merchantrings up the item on the register (e.g., point-of-sale device 150), atotal is presented to the cardholder. The cardholder takes his creditcard (e.g., card 120 a-b) out his wallet and taps it against the digitalcard reader associated with the register. Once the card taps the digitalreader, communication between the digital card reader and the card isinitiated. The card recognizes the data sent from the digital cardreader as being consistent with an EMV data standard. In response, anapplication on the card solely responsible for communicating dataassociated with the EMV data standard transmits only payment data (e.g.data required for facilitating payment) to the digital reader associatedwith the register. The register receives the payment data and processesthe payment. Because the credit card only transmitted payment data, thecardholder is afforded a more secure transaction as data unrelated tothe transaction is not transmitted.

In another case, a cardholder seeks to login to a banking app associatedwith his debit card. The banking app may require multi-levelauthentication, i.e., first level authentication requires ausername/password combination or some form of biometric data (e.g.,optical data, face recognition, thumbprint data) and second levelauthentication requires identity data associated with the card (e.g.,first and last name, social security information) to match at least someof the first level authentication data. The cardholder taps his debitcard against a digital reader associated with his smartphone (e.g.,mobile device 140). Once the debit card taps the digital reader,communication between the digital card reader and the debit card isinitiated. The debit card recognizes the data sent from the digital cardreader as being consistent with an NDEF data standard. In response, anapplication on the debit card solely responsible for communicating dataassociated with the NDEF data standard transmits only identificationdata (e.g., data required for facilitating identification/authenticationpurposes) to the digital reader associated with the smartphone. Thesmartphone, via an application, receives the identification data andauthenticates the cardholder's identity (e.g., compares theidentification data to first level authentication data). Because thedebit card only transmitted identification data, the cardholder isafforded a more secure transaction as data unrelated to authenticationis not transmitted.

We claim:
 1. A card comprising: an antenna; a radio frequencyidentification (RFID) chip; one or more processors; and a non-transitorymemory, including a first application, in communication with the one ormore processors and storing instructions for the first application that,when executed, cause the one or more processors to perform the steps of:receiving, at the antenna, first data from a first external device;determining that the first data comprises transaction data; sending,using the first application, payment data to the first external device;the non-transitory memory, including a second application, incommunication with the one or more processors and storing instructionsfor the second application that, when executed, cause the one or moreprocessors to perform the steps of: receiving, at the antenna, seconddata from a second external device; determining that the second datacomprises a request for identification data; and sending, using thesecond application, identification data to the second external device.2. The card of claim 1, wherein the transaction data comprises EuropayMastercard Visa (EMV) data.
 3. The card of claim 1, wherein theidentification data comprises near field communication data exchangeformat (NDEF) data.
 4. The card of claim 1, wherein: the firstapplication is unable to access the second data; and the secondapplication is unable to access the first data.
 5. The card of claim 1,wherein the card is a contactless payment card.
 6. The card of claim 1,wherein the card is a contactless identification card.
 7. A cardcomprising: an antenna; a radio frequency identification (RFID) chip;one or more processors; and a non-transitory memory, including one ormore applications, in communication with the one or more processors andstoring instructions that, when executed, cause the one or moreprocessors to perform the steps of: receiving, at the antenna, firstdata from a first external device; determining that the first datacomprises transaction data; sending, using the one or more applications,payment data to the first external device; receiving, at the antenna,second data from a second external device; determining that the seconddata comprises a request for identification data; and sending, using theone or more applications, identification data to the second externaldevice.
 8. The card of claim 7, wherein: the card is a contactlesspayment card; the first external device is a payment terminal; and thepayment data is used to complete a transaction with a payment terminal.9. The card of claim 7, wherein: the card is a contactlessidentification card; and the identification data is used to complete anauthentication process with the second external device.
 10. The card ofclaim 7, wherein: the second external device is a mobile device; and theone or more applications further causes the one or more processors to:communicate with the mobile device using a near field communication(NFC) standard when the RFID chip is within an NFC range of a digitalreader associated with the mobile device; transmit a public key of apublic/private key pair of the card to the mobile device; receive, fromthe mobile device, signing instructions to generate a digital signature;generate the digital signature using a private key of the public/privatekey pair; and transmit the digital signature to the mobile device. 11.The card of claim 7, wherein the transaction data comprises EuropayMastercard Visa (EMV) data.
 12. The card of claim 7, wherein theidentification data comprises near field communication data exchangeformat (NDEF) data.
 13. A method comprising: establishing, with anantenna of a card, a first connection between the card and a firstdevice; receiving, at the antenna, first data from the first device;determining, with a processor of the card, a first data format of thefirst data; transmitting, by a first application of the card, seconddata to the first device in the first data format; establishing, withthe antenna, a second connection between the card and a second device;receiving, at the antenna, third data from the second device;determining, with the processor, a second data format of the third data;and transmitting, by a second application of the card, fourth data tothe second device in the second data format.
 14. The method of claim 13,wherein: the first device is a point-of-sale (POS) device; and the firstdata format is EuroPay-MasterCard-Visa (EMV) data format.
 15. The methodof claim 14, wherein the first data comprises payment data to complete atransaction between the card and the POS device.
 16. The method of claim13, wherein: the second device is a mobile device; and the second dataformat corresponds to a near field communication data exchange format(NDEF) data standard.
 17. The method of claim 16, wherein the seconddata comprises identification data to authenticate the card to themobile device.
 18. The method of claim 17, wherein the identificationdata comprises a message authentication code (MAC) cryptogram.
 19. Themethod of claim 13, wherein: the first application is unable to accessthe second data; and the second application is unable to access thefirst data.
 20. The method of claim 13, further comprising:communicating, using a radio frequency identification (RFID) chip on thecard, with the second device using a near field communication (NFC)standard when the RFID chip is within NFC range of a digital readerassociated with the second device; transmitting, with the antenna, apublic key of a public/private key pair to the second device; receiving,from the second device, instructions to generate a digital signature;generating the digital signature using a private key of thepublic/private key pair; and transmitting the digital signature to thesecond device.